feat: optional login_token boot (token-based launcher login)#50
Closed
Shuu-37 wants to merge 1 commit into
Closed
Conversation
4 tasks
Parse an optional login_token from the --json config and send it in the 0x10 login JSON. When present it stands in for password + OTP (password may be empty), and a username + token (no password) enables autologin. Handle the new LOGIN_ERROR_LAUNCH_TOKEN_INVALID (0x14) result with a 'session expired' message. Backward compatible: login_token is optional; the existing password/trust-token path is unchanged.
Shuu-37
force-pushed
the
feat/launch-token-upstream
branch
from
f2941b2 to
4555240
Compare
This was referenced Jun 28, 2026
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Client-side counterpart to a server change: parse an optional
login_tokenfrom the--jsonconfig and send it in the0x10login JSON, so a launcher can boot the game with a single-use, short-TTL token minted by an external auth service instead of a stored password. This supports launchers built around OAuth/SSO sign-in (e.g. "Login with Discord") where there is an authenticated app session but no game password.Companion server PR: LandSandBoat/server#10421 (adds the
login_tokenrail toxi_connect'sLOGIN_ATTEMPT+ theaccounts_login_tokenstable). This client change is harmless without it (the server simply ignores an unknown JSON field).Changes
g_LoginToken, populated fromjsonGet(jsonData, "login_token")in the--jsonparse block.login_token(no password) now enables autologin, alongside the existing username+password case.0x10login JSON, sendlogin_tokenwhen present (next to the existingtrust_token/trust_this_computerfields). Password may be empty on this path.LOGIN_ERROR_LAUNCH_TOKEN_INVALID = 0x14with a "session expired, log in again from the launcher" message and clear the token.Backward compatibility
login_tokenis optional. When absent, the existing username/password and trust-token paths are completely unchanged. No protocol version bump.Notes for reviewers
mainrather than only downstream.